VLESS config: Fix validateOutboundTransportSecurity() - #6741
Merged
Conversation
Member
|
既然拿的是解析过的 VLESS 配置,也就是说外面的 enc 字段已经被 copy 进 account 了,改成只检测 account 内的 enc 就行了 |
Member
Author
|
Users 是个 []json.RawMessage 还得抄一遍json解析 |
Member
|
|
Member
Author
|
还有 "外面的 enc 字段已经被 copy 进 account 了" 是不存在的 它看的原始结构体不是解析出的proto address可以用只是以前的代码刚好和这个PR一样会回填结构体而已 |
Member
|
我再看看,你先搞一下 #6739 (comment) 吧,那个 PR 先合并 |
Member
Author
|
已经在同一个地方回填了 应该和你想的一样 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
被account解析恶心到了 要重新解析出来得把文件再抄一遍 这样虽然丑但是是最简单的了